Visual aura around field of view

ABSTRACT

A wearable device can have a field of view through which a user can perceive real or virtual objects. The device can display a visual aura representing contextual information associated with an object that is outside the user&#39;s field of view. The visual aura can be displayed near an edge of the field of view and can dynamically change as the contextual information associated with the object changes, e.g., the relative position of the object and the user (or the user&#39;s field of view) changes.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/491,571, filed on Apr. 19, 2017, entitled “VISUAL AURA AROUND FIELDOF VIEW,” which claims the benefit of priority under 35 U.S.C. § 119(e)to U.S. Provisional Application No. 62/325,685, filed on Apr. 21, 2016,entitled “RENDERING AURAS FOR OBJECTS IN AN AUGMENTED OR VIRTUAL REALITYENVIRONMENT,” which is hereby incorporated by reference herein in itsentirety.

FIELD

The present disclosure relates to virtual reality and augmented realityimaging and visualization systems and more particularly to informingusers of objects in an environment.

BACKGROUND

Modern computing and display technologies have facilitated thedevelopment of systems for so called “virtual reality”, “augmentedreality”, or “mixed reality” experiences, wherein digitally reproducedimages or portions thereof are presented to a user in a manner whereinthey seem to be, or may be perceived as, real. A virtual reality, or“VR”, scenario typically involves presentation of digital or virtualimage information without transparency to other actual real-world visualinput; an augmented reality, or “AR”, scenario typically involvespresentation of digital or virtual image information as an augmentationto visualization of the actual world around the user; a mixed reality,or “MR”, related to merging real and virtual worlds to produce newenvironments where physical and virtual objects co-exist and interact inreal time. As it turns out, the human visual perception system is verycomplex, and producing a VR, AR, or MR technology that facilitates acomfortable, natural-feeling, rich presentation of virtual imageelements amongst other virtual or real-world imagery elements ischallenging. Systems and methods disclosed herein address variouschallenges related to VR, AR and MR technology.

SUMMARY OF THE INVENTION

In one embodiment, a system for providing an indication of aninteractable object in a three-dimensional (3D) environment of a user isdisclosed. The system can comprise a display system of a wearable deviceconfigured to present a three-dimensional view to a user and permit auser interaction with objects in a field of regard (FOR) of a user. TheFOR can comprise a portion of the environment around the user that iscapable of being perceived by the user via the display system. Thesystem can also comprise a sensor configured to acquire data associatedwith a pose of the user and a hardware processor in communication withthe sensor and the display system. The hardware processor can beprogrammed to: determine a pose of the user based on the data acquiredby the sensor; determine a field of view (FOV) of the user based atleast partly on the pose of the user, the FOV comprising a portion ofthe FOR that is capable of being perceived at a given time by the uservia the display system; identify an interactable object located outsideof the FOV of the user; access contextual information associated withthe interactable object; determine a visual representation of an aurabased on the contextual information; and render the visualrepresentation of the aura such that at least a portion of the visualaura perceivable by the user is on an edge of the FOV of the user.

In another embodiment, a method for providing an indication of aninteractable object in a three-dimensional (3D) environment of a user isdisclosed. The method may be performed under control of a wearabledevice having a display system configured to present a three-dimensional(3D) view to a user and permit a user interaction with objects in afield of regard (FOR) of a user where the FOR can comprise a portion ofthe environment around the user that is capable of being perceived bythe user via the display system; a sensor configured to acquire dataassociated with a pose of the user; and a hardware processor incommunication with the sensor and the display system. The method cancomprise: determining a field of view (FOV) of the user based at leastpartly on the pose of the user, the FOV comprising a portion of the FORthat is capable of being perceived at a given time by the user via thedisplay system; identifying an interactable object located outside ofthe FOV of the user; accessing contextual information associated withthe interactable object; determining a visual representation of an aurabased on the contextual information; and rendering the visualrepresentation of the aura such that at least a portion of the visualaura perceivable by the user is on an edge of the FOV of the user.

Details of one or more implementations of the subject matter describedin this specification are set forth in the accompanying drawings and thedescription below. Other features, aspects, and advantages will becomeapparent from the description, the drawings, and the claims. Neitherthis summary nor the following detailed description purports to defineor limit the scope of the inventive subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an illustration of a mixed reality scenario with certainvirtual reality objects, and certain physical objects viewed by aperson.

FIG. 2 schematically illustrates an example of a wearable system.

FIG. 3 schematically illustrates aspects of an approach for simulatingthree-dimensional imagery using multiple depth planes.

FIG. 4 schematically illustrates an example of a waveguide stack foroutputting image information to a user.

FIG. 5 shows example exit beams that may be outputted by a waveguide.

FIG. 6 is a schematic diagram showing an optical system including awaveguide apparatus, an optical coupler subsystem to optically couplelight to or from the waveguide apparatus, and a control subsystem, usedin the generation of a multi-focal volumetric display, image, or lightfield.

FIG. 7 is a block diagram of an example of a wearable system.

FIG. 8 is a process flow diagram of an example of a method of renderingvirtual content in relation to recognized objects.

FIG. 9 is a block diagram of another example of a wearable system.

FIG. 10 is a process flow diagram of an example of a method fordetermining user input to a wearable system.

FIG. 11 is a process flow diagram of an example of a method forinteracting with a virtual user interface.

FIG. 12 schematically illustrates an example of virtual objects in afield of view (FOV) and virtual objects in a field of regard (FOR).

FIG. 13 schematically illustrates an example of informing the user of anobject in the user's FOR.

FIG. 14A schematically illustrates a perspective view of visual auras onan edge of an FOV.

FIG. 14B schematically illustrates an example of making a correspondingaura invisible for an object within the user's FOV.

FIGS. 15A and 15B schematically illustrate examples of user experienceswith a visual aura.

FIG. 16 illustrates an example process of rendering a visualrepresentation of a visual aura.

FIG. 17 illustrates an example process of determining a visualrepresentation of the visual aura based on contextual information.

Throughout the drawings, reference numbers may be re-used to indicatecorrespondence between referenced elements. The drawings are provided toillustrate example embodiments described herein and are not intended tolimit the scope of the disclosure. Additionally, the figures in thepresent disclosure are for illustration purposes and are not to scale.Although the figures show the FOV as a rectangle, this presentation ofthe FOV is not intended to be limiting. The 2-dimensional representationof the FOV can be any shape, such as, e.g., a circle, oval, triangle,polygon, a rounded square, in combination or the like.

DETAILED DESCRIPTION Overview

A wearable system can be configured to display augmented or virtualreality content. Accordingly, a user's visual computing experience canbe extended to the 3D environment surrounding the user. However, theuser field of view (FOV) perceived through the wearable system (alsoreferred to as the user's FOV) may be smaller than the natural FOV ofthe human eye or smaller than the entire environment surrounding theuser. Thus, there may be physical or virtual objects in the user'senvironment that are initially outside the user's FOV but which maysubsequently move into the user's FOV or which may subsequently becomeperceivable if the user's pose changes (which will change the user'sFOV). For example, in the context of a game, the user may be trying tofind an avatar of a robot. If the robot is just outside the current FOVof the user, the user will receive no cues from the wearable system thatthe robot is nearby. If the user moves her head slightly, the robot maysuddenly enter the user's FOV, which may be startling to the user.Further, if the user's FOV through the wearable system is relativelysmall, it may prove difficult for the user to find the robot unless theuser turns her head or gazes directly at the robot.

To improve the user's visual experience, the wearable system may informthe user about the objects outside of the user's FOV. For example, thewearable system can render a visual representation of a visual aura fora corresponding object outside of the user's current FOV. The visualrepresentation of the aura can be used to indicate contextualinformation associated with the object, the user's environment, or user.For example, a brighter or larger aura may indicate the object is closerto the FOV whereas a dimmer or smaller aura may indicate the object isfarther from the FOV. Similarly, the color of the aura may be used toindicate the type of the object. For example, an enemy avatar (in avirtual game) may be associated with a red aura while a friendly avatar(in the virtual game) may be associated with a green aura, and a systemnotification may be associated with a blue aura. A portion of the visualaura can be placed on the edge of the user's FOV. The size, shape, orposition of the aura may change as the user's FOV changes or as theobject moves. Accordingly, the visual representation of the aura orchanges to the visual representation of the aura can thereby provide auseful cue to the user about nearby objects that are currently outsidethe user's FOV.

Examples of 3D Display of a Wearable System

A wearable system (also referred to herein as an augmented reality (AR)system) can be configured to present 2D or 3D virtual images to a user.The images may be still images, frames of a video, or a video, incombination or the like. The wearable system can include a wearabledevice that can present a VR, AR, or MR environment, alone or incombination, for user interaction. The wearable device can be ahead-mounted device (HMD) which is used interchangeably as an AR device(ARD).

FIG. 1 depicts an illustration of a mixed reality scenario with certainvirtual reality objects, and certain physical objects viewed by aperson. In FIG. 1, an MR scene 100 is depicted wherein a user of an MRtechnology sees a real-world park-like setting 110 featuring people,trees, buildings in the background, and a concrete platform 120. Inaddition to these items, the user of the MR technology also perceivesthat he “sees” a robot statue 130 standing upon the real-world platform120, and a cartoon-like avatar character 140 flying by which seems to bea personification of a bumble bee, even though these elements do notexist in the real world.

In order for the 3D display to produce a true sensation of depth, andmore specifically, a simulated sensation of surface depth, it may bedesirable for each point in the display's visual field to generate anaccommodative response corresponding to its virtual depth. If theaccommodative response to a display point does not correspond to thevirtual depth of that point, as determined by the binocular depth cuesof convergence and stereopsis, the human eye may experience anaccommodation conflict, resulting in unstable imaging, harmful eyestrain, headaches, and, in the absence of accommodation information,almost a complete lack of surface depth.

VR, AR, and MR experiences can be provided by display systems havingdisplays in which images corresponding to a plurality of depth planesare provided to a viewer. The images may be different for each depthplane (e.g., provide slightly different presentations of a scene orobject) and may be separately focused by the viewer's eyes, therebyhelping to provide the user with depth cues based on the accommodationof the eye required to bring into focus different image features for thescene located on different depth plane or based on observing differentimage features on different depth planes being out of focus. Asdiscussed elsewhere herein, such depth cues provide credible perceptionsof depth.

FIG. 2 illustrates an example of wearable system 200. The wearablesystem 200 includes a display 220, and various mechanical and electronicmodules and systems to support the functioning of display 220. Thedisplay 220 may be coupled to a frame 230, which is wearable by a user,wearer, or viewer 210. The display 220 can be positioned in front of theeyes of the user 210. The display 220 can present AR/VR/MR content to auser. The display 220 can comprise a head mounted display (HMD) that isworn on the head of the user. In some embodiments, a speaker 240 iscoupled to the frame 230 and positioned adjacent the ear canal of theuser (in some embodiments, another speaker, not shown, is positionedadjacent the other ear canal of the user to provide for stereo/shapeablesound control).

The wearable system 200 can include an outward-facing imaging system 464(shown in FIG. 4) which observes the world in the environment around theuser. The wearable system 200 can also include an inward-facing imagingsystem 462 (shown in FIG. 4) which can track the eye movements of theuser. The inward-facing imaging system may track either one eye'smovements or both eyes' movements. The inward-facing imaging system 462may be attached to the frame 230 and may be in electrical communicationwith the processing modules 260 or 270, which may process imageinformation acquired by the inward-facing imaging system to determine,e.g., the pupil diameters or orientations of the eyes, eye movements oreye pose of the user 210.

As an example, the wearable system 200 can use the outward-facingimaging system 464 or the inward-facing imaging system 462 to acquireimages of a pose of the user. The images may be still images, frames ofa video, or a video, in combination or the like.

The display 220 can be operatively coupled 250, such as by a wired leador wireless connectivity, to a local data processing module 260 whichmay be mounted in a variety of configurations, such as fixedly attachedto the frame 230, fixedly attached to a helmet or hat worn by the user,embedded in headphones, or otherwise removably attached to the user 210(e.g., in a backpack-style configuration, in a belt-coupling styleconfiguration).

The local processing and data module 260 may comprise a hardwareprocessor, as well as digital memory, such as non-volatile memory (e.g.,flash memory), both of which may be utilized to assist in theprocessing, caching, and storage of data. The data may include data a)captured from sensors (which may be, e.g., operatively coupled to theframe 230 or otherwise attached to the user 210), such as image capturedevices (e.g., cameras in the inward-facing imaging system or theoutward-facing imaging system), microphones, inertial measurement units(IMUs), accelerometers, compasses, global positioning system (GPS)units, radio devices, or gyroscopes; or b) acquired or processed usingremote processing module 270 or remote data repository 280, possibly forpassage to the display 220 after such processing or retrieval. The localprocessing and data module 260 may be operatively coupled bycommunication links 262 or 264, such as via wired or wirelesscommunication links, to the remote processing module 270 or remote datarepository 280 such that these remote modules are available as resourcesto the local processing and data module 260. In addition, remoteprocessing module 280 and remote data repository 280 may be operativelycoupled to each other.

In some embodiments, the remote processing module 270 may comprise oneor more processors configured to analyze and process data and/or imageinformation. In some embodiments, the remote data repository 280 maycomprise a digital data storage facility, which may be available throughthe internet or other networking configuration in a “cloud” resourceconfiguration. In some embodiments, all data is stored and allcomputations are performed in the local processing and data module,allowing fully autonomous use from a remote module.

The human visual system is complicated and providing a realisticperception of depth is challenging. Without being limited by theory, itis believed that viewers of an object may perceive the object as beingthree-dimensional due to a combination of vergence and accommodation.Vergence movements (i.e., rolling movements of the pupils toward or awayfrom each other to converge the lines of sight of the eyes to fixateupon an object) of the two eyes relative to each other are closelyassociated with focusing (or “accommodation”) of the lenses of the eyes.Under normal conditions, changing the focus of the lenses of the eyes,or accommodating the eyes, to change focus from one object to anotherobject at a different distance will automatically cause a matchingchange in vergence to the same distance, under a relationship known asthe “accommodation-vergence reflex.” Likewise, a change in vergence willtrigger a matching change in accommodation, under normal conditions.Display systems that provide a better match between accommodation andvergence may form more realistic and comfortable simulations ofthree-dimensional imagery.

FIG. 3 illustrates aspects of an approach for simulating athree-dimensional imagery using multiple depth planes. With reference toFIG. 3, objects at various distances from eyes 302 and 304 on the z-axisare accommodated by the eyes 302 and 304 so that those objects are infocus. The eyes 302 and 304 assume particular accommodated states tobring into focus objects at different distances along the z-axis.Consequently, a particular accommodated state may be said to beassociated with a particular one of depth planes 306, with has anassociated focal distance, such that objects or parts of objects in aparticular depth plane are in focus when the eye is in the accommodatedstate for that depth plane. In some embodiments, three-dimensionalimagery may be simulated by providing different presentations of animage for each of the eyes 302 and 304, and also by providing differentpresentations of the image corresponding to each of the depth planes.While shown as being separate for clarity of illustration, it will beappreciated that the fields of view of the eyes 302 and 304 may overlap,for example, as distance along the z-axis increases. In addition, whileshown as flat for the ease of illustration, it will be appreciated thatthe contours of a depth plane may be curved in physical space, such thatall features in a depth plane are in focus with the eye in a particularaccommodated state. Without being limited by theory, it is believed thatthe human eye typically can interpret a finite number of depth planes toprovide depth perception. Consequently, a highly believable simulationof perceived depth may be achieved by providing, to the eye, differentpresentations of an image corresponding to each of these limited numberof depth planes.

Waveguide Stack Assembly

FIG. 4 illustrates an example of a waveguide stack for outputting imageinformation to a user. A wearable system 400 includes a stack ofwaveguides, or stacked waveguide assembly 480 that may be utilized toprovide three-dimensional perception to the eye/brain using a pluralityof waveguides 432 b, 434 b, 436 b, 438 b, 4400 b. In some embodiments,the wearable system 400 may correspond to wearable system 200 of FIG. 2,with FIG. 4 schematically showing some parts of that wearable system 200in greater detail. For example, in some embodiments, the waveguideassembly 480 may be integrated into the display 220 of FIG. 2.

With continued reference to FIG. 4, the waveguide assembly 480 may alsoinclude a plurality of features 458, 456, 454, 452 between thewaveguides. In some embodiments, the features 458, 456, 454, 452 may belenses. In other embodiments, the features 458, 456, 454, 452 may not belenses. Rather, they may simply be spacers (e.g., cladding layers orstructures for forming air gaps).

The waveguides 432 b, 434 b, 436 b, 438 b, 440 b or the plurality oflenses 458, 456, 454, 452 may be configured to send image information tothe eye with various levels of wavefront curvature or light raydivergence. Each waveguide level may be associated with a particulardepth plane and may be configured to output image informationcorresponding to that depth plane. Image injection devices 420, 422,424, 426, 428 may be utilized to inject image information into thewaveguides 440 b, 438 b, 436 b, 434 b, 432 b, each of which may beconfigured to distribute incoming light across each respectivewaveguide, for output toward the eye 410. Light exits an output surfaceof the image injection devices 420, 422, 424, 426, 428 and is injectedinto a corresponding input edge of the waveguides 440 b, 438 b, 436 b,434 b, 432 b. In some embodiments, a single beam of light (e.g., acollimated beam) may be injected into each waveguide to output an entirefield of cloned collimated beams that are directed toward the eye 410 atparticular angles (and amounts of divergence) corresponding to the depthplane associated with a particular waveguide.

In some embodiments, the image injection devices 420, 422, 424, 426, 428are discrete displays that each produce image information for injectioninto a corresponding waveguide 440 b, 438 b, 436 b, 434 b, 432 b,respectively. In some other embodiments, the image injection devices420, 422, 424, 426, 428 are the output ends of a single multiplexeddisplay which may, e.g., pipe image information via one or more opticalconduits (such as fiber optic cables) to each of the image injectiondevices 420, 422, 424, 426, 428.

A controller 460 controls the operation of the stacked waveguideassembly 480 and the image injection devices 420, 422, 424, 426, 428.The controller 460 includes programming (e.g., instructions in anon-transitory computer-readable medium) that regulates the timing andprovision of image information to the waveguides 440 b, 438 b, 436 b,434 b, 432 b. In some embodiments, the controller 460 may be a singleintegral device, or a distributed system connected by wired or wirelesscommunication channels. The controller 460 may be part of the processingmodules 260 or 270 (illustrated in FIG. 2) in some embodiments.

The waveguides 440 b, 438 b, 436 b, 434 b, 432 b may be configured topropagate light within each respective waveguide by total internalreflection (TIR). The waveguides 440 b, 438 b, 436 b, 434 b, 432 b mayeach be planar or have another shape (e.g., curved), with major top andbottom surfaces and edges extending between those major top and bottomsurfaces. In the illustrated configuration, the waveguides 440 b, 438 b,436 b, 434 b, 432 b may each include light extracting optical elements440 a, 438 a, 436 a, 434 a, 432 a that are configured to extract lightout of a waveguide by redirecting the light, propagating within eachrespective waveguide, out of the waveguide to output image informationto the eye 410. Extracted light may also be referred to as outcoupledlight, and light extracting optical elements may also be referred to asoutcoupling optical elements. An extracted beam of light is outputted bythe waveguide at locations at which the light propagating in thewaveguide strikes a light redirecting element. The light extractingoptical elements (440 a, 438 a, 436 a, 434 a, 432 a) may, for example,be reflective or diffractive optical features. While illustrateddisposed at the bottom major surfaces of the waveguides 440 b, 438 b,436 b, 434 b, 432 b for ease of description and drawing clarity, in someembodiments, the light extracting optical elements 440 a, 438 a, 436 a,434 a, 432 a may be disposed at the top or bottom major surfaces, or maybe disposed directly in the volume of the waveguides 440 b, 438 b, 436b, 434 b, 432 b. In some embodiments, the light extracting opticalelements 440 a, 438 a, 436 a, 434 a, 432 a may be formed in a layer ofmaterial that is attached to a transparent substrate to form thewaveguides 440 b, 438 b, 436 b, 434 b, 432 b. In some other embodiments,the waveguides 440 b, 438 b, 436 b, 434 b, 432 b may be a monolithicpiece of material and the light extracting optical elements 440 a, 438a, 436 a, 434 a, 432 a may be formed on a surface or in the interior ofthat piece of material.

With continued reference to FIG. 4, as discussed herein, each waveguide440 b, 438 b, 436 b, 434 b, 432 b is configured to output light to forman image corresponding to a particular depth plane. For example, thewaveguide 432 b nearest the eye may be configured to deliver collimatedlight, as injected into such waveguide 432 b, to the eye 410. Thecollimated light may be representative of the optical infinity focalplane. The next waveguide up 434 b may be configured to send outcollimated light which passes through the first lens 452 (e.g., anegative lens) before it can reach the eye 410. First lens 452 may beconfigured to create a slight convex wavefront curvature so that theeye/brain interprets light coming from that next waveguide up 434 b ascoming from a first focal plane closer inward toward the eye 410 fromoptical infinity. Similarly, the third up waveguide 436 b passes itsoutput light through both the first lens 452 and second lens 454 beforereaching the eye 410. The combined optical power of the first and secondlenses 452 and 454 may be configured to create another incrementalamount of wavefront curvature so that the eye/brain interprets lightcoming from the third waveguide 436 b as coming from a second focalplane that is even closer inward toward the person from optical infinitythan was light from the next waveguide up 434 b.

The other waveguide layers (e.g., waveguides 438 b, 440 b) and lenses(e.g., lenses 456, 458) are similarly configured, with the highestwaveguide 440 b in the stack sending its output through all of thelenses between it and the eye for an aggregate focal powerrepresentative of the closest focal plane to the person. To compensatefor the stack of lenses 458, 456, 454, 452 when viewing/interpretinglight coming from the world 470 on the other side of the stackedwaveguide assembly 480, a compensating lens layer 430 may be disposed atthe top of the stack to compensate for the aggregate power of the lensstack 458, 456, 454, 452 below. Such a configuration provides as manyperceived focal planes as there are available waveguide/lens pairings.Both the light extracting optical elements of the waveguides and thefocusing aspects of the lenses may be static (e.g., not dynamic orelectro-active). In some alternative embodiments, either or both may bedynamic using electro-active features.

With continued reference to FIG. 4, the light extracting opticalelements 440 a, 438 a, 436 a, 434 a, 432 a may be configured to bothredirect light out of their respective waveguides and to output thislight with the appropriate amount of divergence or collimation for aparticular depth plane associated with the waveguide. As a result,waveguides having different associated depth planes may have differentconfigurations of light extracting optical elements, which output lightwith a different amount of divergence depending on the associated depthplane. In some embodiments, as discussed herein, the light extractingoptical elements 440 a, 438 a, 436 a, 434 a, 432 a may be volumetric orsurface features, which may be configured to output light at specificangles. For example, the light extracting optical elements 440 a, 438 a,436 a, 434 a, 432 a may be volume holograms, surface holograms, and/ordiffraction gratings. Light extracting optical elements, such asdiffraction gratings, are described in U.S. Patent Publication No.2015/0178939, published Jun. 25, 2015, which is incorporated byreference herein in its entirety.

In some embodiments, the light extracting optical elements 440 a, 438 a,436 a, 434 a, 432 a are diffractive features that form a diffractionpattern, or “diffractive optical element” (also referred to herein as a“DOE”). Preferably, the DOE has a relatively low diffraction efficiencyso that only a portion of the light of the beam is deflected away towardthe eye 410 with each intersection of the DOE, while the rest continuesto move through a waveguide via total internal reflection. The lightcarrying the image information can thus be divided into a number ofrelated exit beams that exit the waveguide at a multiplicity oflocations and the result is a fairly uniform pattern of exit emissiontoward the eye 304 for this particular collimated beam bouncing aroundwithin a waveguide.

In some embodiments, one or more DOEs may be switchable between “on”state in which they actively diffract, and “off” state in which they donot significantly diffract. For instance, a switchable DOE may comprisea layer of polymer dispersed liquid crystal, in which microdropletscomprise a diffraction pattern in a host medium, and the refractiveindex of the microdroplets can be switched to substantially match therefractive index of the host material (in which case the pattern doesnot appreciably diffract incident light) or the microdroplet can beswitched to an index that does not match that of the host medium (inwhich case the pattern actively diffracts incident light).

In some embodiments, the number and distribution of depth planes ordepth of field may be varied dynamically based on the pupil sizes ororientations of the eyes of the viewer. Depth of field may changeinversely with a viewer's pupil size. As a result, as the sizes of thepupils of the viewer's eyes decrease, the depth of field increases suchthat one plane that is not discernible because the location of thatplane is beyond the depth of focus of the eye may become discernible andappear more in focus with reduction of pupil size and commensurate withthe increase in depth of field. Likewise, the number of spaced apartdepth planes used to present different images to the viewer may bedecreased with the decreased pupil size. For example, a viewer may notbe able to clearly perceive the details of both a first depth plane anda second depth plane at one pupil size without adjusting theaccommodation of the eye away from one depth plane and to the otherdepth plane. These two depth planes may, however, be sufficiently infocus at the same time to the user at another pupil size withoutchanging accommodation.

In some embodiments, the display system may vary the number ofwaveguides receiving image information based upon determinations ofpupil size or orientation, or upon receiving electrical signalsindicative of particular pupil size or orientation. For example, if theuser's eyes are unable to distinguish between two depth planesassociated with two waveguides, then the controller 460 may beconfigured or programmed to cease providing image information to one ofthese waveguides. Advantageously, this may reduce the processing burdenon the system, thereby increasing the responsiveness of the system. Inembodiments in which the DOEs for a waveguide are switchable between theon and off states, the DOEs may be switched to the off state when thewaveguide does receive image information.

In some embodiments, it may be desirable to have an exit beam meet thecondition of having a diameter that is less than the diameter of the eyeof a viewer. However, meeting this condition may be challenging in viewof the variability in size of the viewer's pupils. In some embodiments,this condition is met over a wide range of pupil sizes by varying thesize of the exit beam in response to determinations of the size of theviewer's pupil. For example, as the pupil size decreases, the size ofthe exit beam may also decrease. In some embodiments, the exit beam sizemay be varied using a variable aperture.

The wearable system 400 can include an outward-facing imaging system 464(e.g., a digital camera) that images a portion of the world 470. Thisportion of the world 470 may be referred to as the field of view (FOV)of a world camera and the imaging system 464 is sometimes referred to asan FOV camera. The entire region available for viewing or imaging by aviewer may be referred to as the field of regard (FOR). The FOR mayinclude 4π steradians of solid angle surrounding the wearable system 400because the wearer can move his body, head, or eyes to perceivesubstantially any direction in space. In other contexts, the wearer'smovements may be more constricted, and accordingly the wearer's FOR maysubtend a smaller solid angle. Images obtained from the outward-facingimaging system 464 can be used to track gestures made by the user (e.g.,hand or finger gestures), detect objects in the world 470 in front ofthe user, and so forth.

The wearable system 400 can also include an inward-facing imaging system466 (e.g., a digital camera), which observes the movements of the user,such as the eye movements and the facial movements. The inward-facingimaging system 466 may be used to capture images of the eye 410 todetermine the size and/or orientation of the pupil of the eye 304. Theinward-facing imaging system 466 can be used to obtain images for use indetermining the direction the user is looking (e.g., eye pose) or forbiometric identification of the user (e.g., via iris identification). Insome embodiments, at least one camera may be utilized for each eye, toseparately determine the pupil size or eye pose of each eyeindependently, thereby allowing the presentation of image information toeach eye to be dynamically tailored to that eye. In some otherembodiments, the pupil diameter or orientation of only a single eye 410(e.g., using only a single camera per pair of eyes) is determined andassumed to be similar for both eyes of the user. The images obtained bythe inward-facing imaging system 466 may be analyzed to determine theuser's eye pose or mood, which can be used by the wearable system 400 todecide which audio or visual content should be presented to the user.The wearable system 400 may also determine head pose (e.g., headposition or head orientation) using sensors such as IMUs,accelerometers, gyroscopes, etc.

The wearable system 400 can include a user input device 466 by which theuser can input commands to the controller 460 to interact with thewearable system 400. For example, the user input device 466 can includea trackpad, a touchscreen, a joystick, a multiple degree-of-freedom(DOF) controller, a capacitive sensing device, a game controller, akeyboard, a mouse, a directional pad (D-pad), a wand, a haptic device, atotem (e.g., functioning as a virtual user input device), and so forth.A multi-DOF controller can sense user input in some or all possibletranslations (e.g., left/right, forward/backward, or up/down) orrotations (e.g., yaw, pitch, or roll) of the controller. A multi-DOFcontroller which supports the translation movements may be referred toas a 3DOF while a multi-DOF controller which supports the translationsand rotations may be referred to as 6DOF. In some cases, the user mayuse a finger (e.g., a thumb) to press or swipe on a touch-sensitiveinput device to provide input to the wearable system 400 (e.g., toprovide user input to a user interface provided by the wearable system400). The user input device 466 may be held by the user's hand duringthe use of the wearable system 400. The user input device 466 can be inwired or wireless communication with the wearable system 400.

FIG. 5 shows an example of exit beams outputted by a waveguide. Onewaveguide is illustrated, but it will be appreciated that otherwaveguides in the waveguide assembly 480 may function similarly, wherethe waveguide assembly 480 includes multiple waveguides. Light 520 isinjected into the waveguide 432 b at the input edge 432 c of thewaveguide 432 b and propagates within the waveguide 432 b by TIR. Atpoints where the light 520 impinges on the DOE 432 a, a portion of thelight exits the waveguide as exit beams 510. The exit beams 510 areillustrated as substantially parallel but they may also be redirected topropagate to the eye 410 at an angle (e.g., forming divergent exitbeams), depending on the depth plane associated with the waveguide 432b. It will be appreciated that substantially parallel exit beams may beindicative of a waveguide with light extracting optical elements thatoutcouple light to form images that appear to be set on a depth plane ata large distance (e.g., optical infinity) from the eye 410. Otherwaveguides or other sets of light extracting optical elements may outputan exit beam pattern that is more divergent, which would require the eye410 to accommodate to a closer distance to bring it into focus on theretina and would be interpreted by the brain as light from a distancecloser to the eye 410 than optical infinity.

FIG. 6 is a schematic diagram showing an optical system including awaveguide apparatus, an optical coupler subsystem to optically couplelight to or from the waveguide apparatus, and a control subsystem, usedin the generation of a multi-focal volumetric display, image, or lightfield. The optical system can include a waveguide apparatus, an opticalcoupler subsystem to optically couple light to or from the waveguideapparatus, and a control subsystem. The optical system can be used togenerate a multi-focal volumetric, image, or light field. The opticalsystem can include one or more primary planar waveguides 632 a (only oneis shown in FIG. 6) and one or more DOEs 632 b associated with each ofat least some of the primary waveguides 632 a. The planar waveguides 632b can be similar to the waveguides 432 b, 434 b, 436 b, 438 b, 440 bdiscussed with reference to FIG. 4. The optical system may employ adistribution waveguide apparatus to relay light along a first axis(vertical or Y-axis in view of FIG. 6), and expand the light's effectiveexit pupil along the first axis (e.g., Y-axis). The distributionwaveguide apparatus may, for example, include a distribution planarwaveguide 622 b and at least one DOE 622 a (illustrated by doubledash-dot line) associated with the distribution planar waveguide 622 b.The distribution planar waveguide 622 b may be similar or identical inat least some respects to the primary planar waveguide 632 b, having adifferent orientation therefrom. Likewise, at least one DOE 622 a may besimilar or identical in at least some respects to the DOE 632 a. Forexample, the distribution planar waveguide 622 b or DOE 622 a may becomprised of the same materials as the primary planar waveguide 632 b orDOE 632 a, respectively. Embodiments of the optical display system 600shown in FIG. 6 can be integrated into the wearable system 200 shown inFIG. 2.

The relayed and exit-pupil expanded light may be optically coupled fromthe distribution waveguide apparatus into the one or more primary planarwaveguides 632 b. The primary planar waveguide 632 b can relay lightalong a second axis, preferably orthogonal to first axis (e.g.,horizontal or X-axis in view of FIG. 6). Notably, the second axis can bea non-orthogonal axis to the first axis. The primary planar waveguide632 b expands the light's effective exit pupil along that second axis(e.g., X-axis). For example, the distribution planar waveguide 622 b canrelay and expand light along the vertical or Y-axis, and pass that lightto the primary planar waveguide 632 b which can relay and expand lightalong the horizontal or X-axis.

The optical system may include one or more sources of colored light(e.g., red, green, and blue laser light) 610 which may be opticallycoupled into a proximal end of a single mode optical fiber 640. A distalend of the optical fiber 640 may be threaded or received through ahollow tube 642 of piezoelectric material. The distal end protrudes fromthe tube 642 as fixed-free flexible cantilever 644. The piezoelectrictube 642 can be associated with four quadrant electrodes (notillustrated). The electrodes may, for example, be plated on the outside,outer surface or outer periphery or diameter of the tube 642. A coreelectrode (not illustrated) may also be located in a core, center, innerperiphery or inner diameter of the tube 642.

Drive electronics 650, for example electrically coupled via wires 660,drive opposing pairs of electrodes to bend the piezoelectric tube 642 intwo axes independently. The protruding distal tip of the optical fiber644 has mechanical modes of resonance. The frequencies of resonance candepend upon a diameter, length, and material properties of the opticalfiber 644. By vibrating the piezoelectric tube 642 near a first mode ofmechanical resonance of the fiber cantilever 644, the fiber cantilever644 can be caused to vibrate, and can sweep through large deflections.

By stimulating resonant vibration in two axes, the tip of the fibercantilever 644 is scanned biaxially in an area filling two-dimensional(2D) scan. By modulating an intensity of light source(s) 610 insynchrony with the scan of the fiber cantilever 644, light emerging fromthe fiber cantilever 644 can form an image. Descriptions of such a setup are provided in U.S. Patent Publication No. 2014/0003762, which isincorporated by reference herein in its entirety.

A component of an optical coupler subsystem can collimate the lightemerging from the scanning fiber cantilever 644. The collimated lightcan be reflected by mirrored surface 648 into the narrow distributionplanar waveguide 622 b which contains the at least one diffractiveoptical element (DOE) 622 a. The collimated light can propagatevertically (relative to the view of FIG. 6) along the distributionplanar waveguide 622 b by TIR, and in doing so repeatedly intersectswith the DOE 622 a. The DOE 622 a preferably has a low diffractionefficiency. This can cause a fraction (e.g., 10%) of the light to bediffracted toward an edge of the larger primary planar waveguide 632 bat each point of intersection with the DOE 622 a, and a fraction of thelight to continue on its original trajectory down the length of thedistribution planar waveguide 622 b via TIR.

At each point of intersection with the DOE 622 a, additional light canbe diffracted toward the entrance of the primary waveguide 632 b. Bydividing the incoming light into multiple outcoupled sets, the exitpupil of the light can be expanded vertically by the DOE 4 in thedistribution planar waveguide 622 b. This vertically expanded lightcoupled out of distribution planar waveguide 622 b can enter the edge ofthe primary planar waveguide 632 b.

Light entering primary waveguide 632 b can propagate horizontally(relative to the view of FIG. 6) along the primary waveguide 632 b viaTIR. As the light intersects with DOE 632 a at multiple points as itpropagates horizontally along at least a portion of the length of theprimary waveguide 632 b via TIR. The DOE 632 a may advantageously bedesigned or configured to have a phase profile that is a summation of alinear diffraction pattern and a radially symmetric diffractive pattern,to produce both deflection and focusing of the light. The DOE 632 a mayadvantageously have a low diffraction efficiency (e.g., 10%), so thatonly a portion of the light of the beam is deflected toward the eye ofthe view with each intersection of the DOE 632 a while the rest of thelight continues to propagate through the primary waveguide 632 b viaTIR.

At each point of intersection between the propagating light and the DOE632 a, a fraction of the light is diffracted toward the adjacent face ofthe primary waveguide 632 b allowing the light to escape the TIR, andemerge from the face of the primary waveguide 632 b. In someembodiments, the radially symmetric diffraction pattern of the DOE 632 aadditionally imparts a focus level to the diffracted light, both shapingthe light wavefront (e.g., imparting a curvature) of the individual beamas well as steering the beam at an angle that matches the designed focuslevel.

Accordingly, these different pathways can cause the light to be coupledout of the primary planar waveguide 632 b by a multiplicity of DOEs 632a at different angles, focus levels, and/or yielding different fillpatterns at the exit pupil. Different fill patterns at the exit pupilcan be beneficially used to create a light field display with multipledepth planes. Each layer in the waveguide assembly or a set of layers(e.g., 3 layers) in the stack may be employed to generate a respectivecolor (e.g., red, blue, green). Thus, for example, a first set of threeadjacent layers may be employed to respectively produce red, blue andgreen light at a first focal depth. A second set of three adjacentlayers may be employed to respectively produce red, blue and green lightat a second focal depth. Multiple sets may be employed to generate afull 3D or 4D color image light field with various focal depths.

Other Components of the Wearable System

In many implementations, the wearable system may include othercomponents in addition or in alternative to the components of thewearable system described above. The wearable system may, for example,include one or more haptic devices or components. The haptic devices orcomponents may be operable to provide a tactile sensation to a user. Forexample, the haptic devices or components may provide a tactilesensation of pressure or texture when touching virtual content (e.g.,virtual objects, virtual tools, other virtual constructs). The tactilesensation may replicate a feel of a physical object which a virtualobject represents, or may replicate a feel of an imagined object orcharacter (e.g., a dragon) which the virtual content represents. In someimplementations, haptic devices or components may be worn by the user(e.g., a user wearable glove). In some implementations, haptic devicesor components may be held by the user.

The wearable system may, for example, include one or more physicalobjects which are manipulable by the user to allow input or interactionwith the wearable system. These physical objects may be referred toherein as totems. Some totems may take the form of inanimate objects,such as for example, a piece of metal or plastic, a wall, a surface oftable. In certain implementations, the totems may not actually have anyphysical input structures (e.g., keys, triggers, joystick, trackball,rocker switch). Instead, the totem may simply provide a physicalsurface, and the wearable system may render a user interface so as toappear to a user to be on one or more surfaces of the totem. Forexample, the wearable system may render an image of a computer keyboardand trackpad to appear to reside on one or more surfaces of a totem. Forexample, the wearable system may render a virtual computer keyboard andvirtual trackpad to appear on a surface of a thin rectangular plate ofaluminum which serves as a totem. The rectangular plate does not itselfhave any physical keys or trackpad or sensors. However, the wearablesystem may detect user manipulation or interaction or touches with therectangular plate as selections or inputs made via the virtual keyboardor virtual trackpad. The user input device 466 (shown in FIG. 4) may bean embodiment of a totem, which may include a trackpad, a touchpad, atrigger, a joystick, a trackball, a rocker or virtual switch, a mouse, akeyboard, a multi-degree-of-freedom controller, or another physicalinput device. A user may use the totem, alone or in combination withposes, to interact with the wearable system or other users.

Examples of haptic devices and totems usable with the wearable devices,HMD, and display systems of the present disclosure are described in U.S.Patent Publication No. 2015/0016777, which is incorporated by referenceherein in its entirety.

Example Wearable Systems, Environments, and Interfaces

A wearable system may employ various mapping related techniques in orderto achieve high depth of field in the rendered light fields. In mappingout the virtual world, it is advantageous to know all the features andpoints in the real world to accurately portray virtual objects inrelation to the real world. To this end, FOV images captured from usersof the wearable system can be added to a world model by including newpictures that convey information about various points and features ofthe real world. For example, the wearable system can collect a set ofmap points (such as 2D points or 3D points) and find new map points torender a more accurate version of the world model. The world model of afirst user can be communicated (e.g., over a network such as a cloudnetwork) to a second user so that the second user can experience theworld surrounding the first user.

FIG. 7 is a block diagram of an example of an MR environment 700. The MRenvironment 700 may be configured to receive input (e.g., visual input702 from the user's wearable system, stationary input 704 such as roomcameras, sensory input 706 from various sensors, gestures, totems, eyetracking, user input from the user input device 466 etc.) from one ormore user wearable systems (e.g., wearable system 200 or display system220) or stationary room systems (e.g., room cameras, etc.). The wearablesystems can use various sensors (e.g., accelerometers, gyroscopes,temperature sensors, movement sensors, depth sensors, GPS sensors,inward-facing imaging system, outward-facing imaging system, etc.) todetermine the location and various other attributes of the environmentof the user. This information may further be supplemented withinformation from stationary cameras in the room that may provide imagesor various cues from a different point of view. The image data acquiredby the cameras (such as the room cameras and/or the cameras of theoutward-facing imaging system) may be reduced to a set of mappingpoints.

One or more object recognizers 708 can crawl through the received data(e.g., the collection of points) and recognize or map points, tagimages, attach semantic information to objects with the help of a mapdatabase 710. The map database 710 may comprise various points collectedover time and their corresponding objects. The various devices and themap database can be connected to each other through a network (e.g.,LAN, WAN, etc.) to access the cloud.

Based on this information and collection of points in the map database,the object recognizers 708 a to 708 n may recognize objects in anenvironment. For example, the object recognizers can recognize faces,persons, windows, walls, user input devices, televisions, other objectsin the user's environment, etc. One or more object recognizers may bespecialized for object with certain characteristics. For example, theobject recognizer 708 a may be used to recognizer faces, while anotherobject recognizer may be used recognize totems.

The object recognitions may be performed using a variety of computervision techniques. For example, the wearable system can analyze theimages acquired by the outward-facing imaging system 464 (shown in FIG.4) to perform scene reconstruction, event detection, video tracking,object recognition, object pose estimation, learning, indexing, motionestimation, or image restoration, etc. One or more computer visionalgorithms may be used to perform these tasks. Non-limiting examples ofcomputer vision algorithms include: Scale-invariant feature transform(SIFT), speeded up robust features (SURF), oriented FAST and rotatedBRIEF (ORB), binary robust invariant scalable keypoints (BRISK), fastretina keypoint (FREAK), Viola-Jones algorithm, Eigenfaces approach,Lucas-Kanade algorithm, Horn-Schunk algorithm, Mean-shift algorithm,visual simultaneous location and mapping (vSLAM) techniques, asequential Bayesian estimator (e.g., Kalman filter, extended Kalmanfilter, etc.), bundle adjustment, Adaptive thresholding (and otherthresholding techniques), Iterative Closest Point (ICP), Semi GlobalMatching (SGM), Semi Global Block Matching (SGBM), Feature PointHistograms, various machine learning algorithms (such as e.g., supportvector machine, k-nearest neighbors algorithm, Naive Bayes, neuralnetwork (including convolutional or deep neural networks), or othersupervised/unsupervised models, etc.), and so forth.

The object recognitions can additionally or alternatively be performedby a variety of machine learning algorithms. Once trained, the machinelearning algorithm can be stored by the HMD. Some examples of machinelearning algorithms can include supervised or non-supervised machinelearning algorithms, including regression algorithms (such as, forexample, Ordinary Least Squares Regression), instance-based algorithms(such as, for example, Learning Vector Quantization), decision treealgorithms (such as, for example, classification and regression trees),Bayesian algorithms (such as, for example, Naive Bayes), clusteringalgorithms (such as, for example, k-means clustering), association rulelearning algorithms (such as, for example, a-priori algorithms),artificial neural network algorithms (such as, for example, Perceptron),deep learning algorithms (such as, for example, Deep Boltzmann Machine,or deep neural network), dimensionality reduction algorithms (such as,for example, Principal Component Analysis), ensemble algorithms (suchas, for example, Stacked Generalization), and/or other machine learningalgorithms. In some embodiments, individual models can be customized forindividual data sets. For example, the wearable device can generate orstore a base model. The base model may be used as a starting point togenerate additional models specific to a data type (e.g., a particularuser in the telepresence session), a data set (e.g., a set of additionalimages obtained of the user in the telepresence session), conditionalsituations, or other variations. In some embodiments, the wearable HMDcan be configured to utilize a plurality of techniques to generatemodels for analysis of the aggregated data. Other techniques may includeusing pre-defined thresholds or data values.

Based on this information and collection of points in the map database,the object recognizers 708 a to 708 n may recognize objects andsupplement objects with semantic information to give life to theobjects. For example, if the object recognizer recognizes a set ofpoints to be a door, the system may attach some semantic information(e.g., the door has a hinge and has a 90 degree movement about thehinge). If the object recognizer recognizes a set of points to be amirror, the system may attach semantic information that the mirror has areflective surface that can reflect images of objects in the room. Overtime the map database grows as the system (which may reside locally ormay be accessible through a wireless network) accumulates more data fromthe world. Once the objects are recognized, the information may betransmitted to one or more wearable systems. For example, the MRenvironment 700 may include information about a scene happening inCalifornia. The environment 700 may be transmitted to one or more usersin New York. Based on data received from an FOV camera and other inputs,the object recognizers and other software components can map the pointscollected from the various images, recognize objects etc., such that thescene may be accurately “passed over” to a second user, who may be in adifferent part of the world. The environment 700 may also use atopological map for localization purposes.

FIG. 8 is a process flow diagram of an example of a method 800 ofrendering virtual content in relation to recognized objects. The method800 describes how a virtual scene may be represented to a user of thewearable system. The user may be geographically remote from the scene.For example, the user may be New York, but may want to view a scene thatis presently going on in California, or may want to go on a walk with afriend who resides in California.

At block 810, the wearable system may receive input from the user andother users regarding the environment of the user. This may be achievedthrough various input devices, and knowledge already possessed in themap database. The user's FOV camera, sensors, GPS, eye tracking, etc.,convey information to the system at block 810. The system may determinesparse points based on this information at block 820. The sparse pointsmay be used in determining pose data (e.g., head pose, eye pose, bodypose, or hand gestures) that can be used in displaying and understandingthe orientation and position of various objects in the user'ssurroundings. The object recognizers 708 a-708 n may crawl through thesecollected points and recognize one or more objects using a map databaseat block 830. This information may then be conveyed to the user'sindividual wearable system at block 840, and the desired virtual scenemay be accordingly displayed to the user at block 850. For example, thedesired virtual scene (e.g., user in CA) may be displayed at theappropriate orientation, position, etc., in relation to the variousobjects and other surroundings of the user in New York.

FIG. 9 is a block diagram of another example of a wearable system. Inthis example, the wearable system 900 comprises a map, which may includemap data for the world. The map may partly reside locally on thewearable system, and may partly reside at networked storage locationsaccessible by wired or wireless network (e.g., in a cloud system). Apose process 910 may be executed on the wearable computing architecture(e.g., processing module 260 or controller 460) and utilize data fromthe map to determine position and orientation of the wearable computinghardware or user. Pose data may be computed from data collected on thefly as the user is experiencing the system and operating in the world.The data may comprise images, data from sensors (such as inertialmeasurement units, which generally comprise accelerometer and gyroscopecomponents) and surface information pertinent to objects in the real orvirtual environment.

A sparse point representation may be the output of a simultaneouslocalization and mapping (SLAM or V-SLAM, referring to a configurationwherein the input is images/visual only) process. The system can beconfigured to not only find out where in the world the variouscomponents are, but what the world is made of. Pose may be a buildingblock that achieves many goals, including populating the map and usingthe data from the map.

In one embodiment, a sparse point position may not be completelyadequate on its own, and further information may be needed to produce amultifocal AR, VR, or MR experience. Dense representations, generallyreferring to depth map information, may be utilized to fill this gap atleast in part. Such information may be computed from a process referredto as Stereo 940, wherein depth information is determined using atechnique such as triangulation or time-of-flight sensing. Imageinformation and active patterns (such as infrared patterns created usingactive projectors) may serve as input to the Stereo process 940. Asignificant amount of depth map information may be fused together, andsome of this may be summarized with a surface representation. Forexample, mathematically definable surfaces may be efficient (e.g.,relative to a large point cloud) and digestible inputs to otherprocessing devices like game engines. Thus, the output of the stereoprocess (e.g., a depth map) 940 may be combined in the fusion process930. Pose may be an input to this fusion process 930 as well, and theoutput of fusion 930 becomes an input to populating the map process 920.Sub-surfaces may connect with each other, such as in topographicalmapping, to form larger surfaces, and the map becomes a large hybrid ofpoints and surfaces.

To resolve various aspects in a mixed reality process 960, variousinputs may be utilized. For example, in the embodiment depicted in FIG.9, Game parameters may be inputs to determine that the user of thesystem is playing a monster battling game with one or more monsters atvarious locations, monsters dying or running away under variousconditions (such as if the user shoots the monster), walls or otherobjects at various locations, and the like. The world map may includeinformation regarding where such objects are relative to each other, tobe another valuable input to mixed reality. Pose relative to the worldbecomes an input as well and plays a key role to almost any interactivesystem.

Controls or inputs from the user are another input to the wearablesystem 900. As described herein, user inputs can include visual input,gestures, totems, audio input, sensory input, etc. In order to movearound or play a game, for example, the user may need to instruct thewearable system 900 regarding what he or she wants to do. Beyond justmoving oneself in space, there are various forms of user controls thatmay be utilized. In one embodiment, a totem (e.g. a user input device),or an object such as a toy gun may be held by the user and tracked bythe system. The system preferably will be configured to know that theuser is holding the item and understand what kind of interaction theuser is having with the item (e.g., if the totem or object is a gun, thesystem may be configured to understand location and orientation, as wellas whether the user is clicking a trigger or other sensed button orelement which may be equipped with a sensor, such as an IMU, which mayassist in determining what is going on, even when such activity is notwithin the field of view of any of the cameras.)

Hand gesture tracking or recognition may also provide input information.The wearable system 900 may be configured to track and interpret handgestures for button presses, for gesturing left or right, stop, grab,hold, etc. For example, in one configuration, the user may want to flipthrough emails or a calendar in a non-gaming environment, or do a “fistbump” with another person or player. The wearable system 900 may beconfigured to leverage a minimum amount of hand gesture, which may ormay not be dynamic. For example, the gestures may be simple staticgestures like open hand for stop, thumbs up for ok, thumbs down for notok; or a hand flip right, or left, or up/down for directional commands.

Eye tracking is another input (e.g., tracking where the user is lookingto control the display technology to render at a specific depth orrange). In one embodiment, vergence of the eyes may be determined usingtriangulation, and then using a vergence/accommodation model developedfor that particular person, accommodation may be determined.

With regard to the camera systems, the example wearable system 900 shownin FIG. 9 can include three pairs of cameras: a relative wide FOV orpassive SLAM pair of cameras arranged to the sides of the user's face, adifferent pair of cameras oriented in front of the user to handle thestereo imaging process 940 and also to capture hand gestures andtotem/object tracking in front of the user's face. The FOV cameras andthe pair of cameras for the stereo process 940 may be a part of theoutward-facing imaging system 464 (shown in FIG. 4). The wearable system900 can include eye tracking cameras (which may be a part of aninward-facing imaging system 462 shown in FIG. 4) oriented toward theeyes of the user in order to triangulate eye vectors and otherinformation. The wearable system 900 may also comprise one or moretextured light projectors (such as infrared (IR) projectors) to injecttexture into a scene.

FIG. 10 is a process flow diagram of an example of a method 1000 fordetermining user input to a wearable system. In this example, the usermay interact with a totem. The user may have multiple totems. Forexample, the user may have designated one totem for a social mediaapplication, another totem for playing games, etc. At block 1010, thewearable system may detect a motion of a totem. The movement of thetotem may be recognized through the outward facing system or may bedetected through sensors (e.g., haptic glove, image sensors, handtracking devices, eye-tracking cameras, head pose sensors, etc.).

Based at least partly on the detected gesture, eye pose, head pose, orinput through the totem, the wearable system detects a position,orientation, and/or movement of the totem (or the user's eyes or head orgestures) with respect to a reference frame, at block 1020. Thereference frame may be a set of map points based on which the wearablesystem translates the movement of the totem (or the user) to an actionor command. At block 1030, the user's interaction with the totem ismapped. Based on the mapping of the user interaction with respect to thereference frame 1020, the system determines the user input at block1040.

For example, the user may move a totem or physical object back and forthto signify turning a virtual page and moving on to a next page or movingfrom one user interface (UI) display screen to another UI screen. Asanother example, the user may move their head or eyes to look atdifferent real or virtual objects in the user's FOR. If the user's gazeat a particular real or virtual object is longer than a threshold time,the real or virtual object may be selected as the user input. In someimplementations, the vergence of the user's eyes can be tracked and anaccommodation/vergence model can be used to determine the accommodationstate of the user's eyes, which provides information on a depth plane onwhich the user is focusing. In some implementations, the wearable systemcan use ray casting techniques to determine which real or virtualobjects are along the direction of the user's head pose or eye pose. Invarious implementations, the ray casting techniques can include castingthin, pencil rays with substantially little transverse width or castingrays with substantial transverse width (e.g., cones or frustums).

The user interface may be projected by the display system as describedherein (such as the display 220 in FIG. 2). It may also be displayedusing a variety of other techniques such as one or more projectors. Theprojectors may project images onto a physical object such as a canvas ora globe. Interactions with user interface may be tracked using one ormore cameras external to the system or part of the system (such as,e.g., using the inward-facing imaging system 462 or the outward-facingimaging system 464).

FIG. 11 is a process flow diagram of an example of a method 1100 forinteracting with a virtual user interface. The method 1100 may beperformed by the wearable system described herein.

At block 1110, the wearable system may identify a particular UI. Thetype of UI may be predetermined by the user. The wearable system mayidentify that a particular UI needs to be populated based on a userinput (e.g., gesture, visual data, audio data, sensory data, directcommand, etc.). At block 1120, the wearable system may generate data forthe virtual UI. For example, data associated with the confines, generalstructure, shape of the UI etc., may be generated. In addition, thewearable system may determine map coordinates of the user's physicallocation so that the wearable system can display the UI in relation tothe user's physical location. For example, if the UI is body centric,the wearable system may determine the coordinates of the user's physicalstance, head pose, or eye pose such that a ring UI can be displayedaround the user or a planar UI can be displayed on a wall or in front ofthe user. If the UI is hand centric, the map coordinates of the user'shands may be determined. These map points may be derived through datareceived through the FOV cameras, sensory input, or any other type ofcollected data.

At block 1130, the wearable system may send the data to the display fromthe cloud or the data may be sent from a local database to the displaycomponents. At block 1140, the UI is displayed to the user based on thesent data. For example, a light field display can project the virtual UIinto one or both of the user's eyes. Once the virtual UI has beencreated, the wearable system may simply wait for a command from the userto generate more virtual content on the virtual UI at block 1150. Forexample, the UI may be a body centric ring around the user's body. Thewearable system may then wait for the command (a gesture, a head or eyemovement, input from a user input device, etc.), and if it is recognized(block 1160), virtual content associated with the command may bedisplayed to the user (block 1170). As an example, the wearable systemmay wait for user's hand gestures before mixing multiple steam tracks.

Additional examples of wearable systems, UIs, and user experiences (UX)are described in U.S. Patent Publication No. 2015/0016777, which isincorporated by reference herein in its entirety.

Examples Objects in the Field of Regard (FOR) and Field of View (FOV)

FIG. 12 schematically illustrates an example of virtual objects in afield of view (FOV) and virtual objects in a field of regard (FOR). Asdiscussed with reference to FIG. 4, the FOR comprises a portion of theenvironment around the user that is capable of being perceived by theuser via the wearable system. For a head-mounted augmented realitydevice (ARD), the FOR may include substantially all of the 4π steradiansolid angle surrounding the wearer, because the wearer can move herbody, head, or eyes to perceive substantially any direction in space. Inother contexts, the user's movements may be more constricted, andaccordingly the user's FOR may subtend a smaller solid angle.

In FIG. 12, the FOR 1200 can include a group of objects (e.g. 1210,1220, 1230, 1242, and 1244) which can be perceived by the user via thewearable system. The objects within the user's FOR 1200 may be virtualor physical objects. For example, the user's FOR 1200 may includephysical object such as a chair, a sofa, a wall, etc. The virtualobjects may include operating system objects such as e.g., a recycle binfor deleted files, a terminal for inputting commands, a file manager foraccessing files or directories, an icon, a menu, an application foraudio or video streaming, a notification from an operating system, andso on. The virtual objects may also include objects in an applicationsuch as e.g., avatars, virtual objects in games, graphics or images,etc. Some virtual objects can be both an operating system object and anobject in an application. In some embodiments, the wearable system canadd virtual elements to the existing physical objects. For example, thewearable system may add a virtual menu associated with a television inthe room, where the virtual menu may give the user the option to turn onor change the channels of the television using the wearable system.

A virtual object may be a three-dimensional (3D), two-dimensional (2D),or one-dimensional (1D) object. The objects in the user's FOR can bepart of a world map as described with reference to FIG. 9. Dataassociated with objects (e.g. location, semantic information,properties, etc.) can be stored in a variety of data structures such as,e.g., arrays, lists, trees, hashes, graphs, and so on. The index of eachstored object, wherein applicable, may be determined, for example, bythe location of the object. For example, the data structure may indexthe objects by a single coordinate such as the object's distance from afiducial position (e.g., how far to the left or right of the fiducialposition, how far from the top or bottom of the fiducial position, orhow far depth-wise from the fiducial position). The fiducial positionmay be determined based on the user's position (such as the position ofthe user's head). The fiducial position may also be determined based onthe position of a virtual or physical object (such as a targetinteractable object) in the user's environment. This way, the 3D spacein the user's environment may be collapsed into a 2D user interfacewhere the virtual objects are arranged in accordance with the object'sdistance from the fiducial position.

Within the FOR 1200, the portion of the world that a user perceives at agiven time is referred to as the FOV 1250 (e.g., the FOV 1250 mayencompass the portion of the FOR that the user is currently lookingtoward). In FIG. 12, the FOV 1250 is schematically illustrated by dashedline 1252. The user of the wearable system can perceive multiple objectsin the FOV 1250, such as the object 1242, the object 1244, and a portionof the object 1230. The FOV can depend on the size or opticalcharacteristics of the display of a wearable device. For example, an ARdisplay (e.g., the display 220 in FIG. 2) may include optics (such as,e.g., the stacked waveguide assembly 480 in FIG. 4 or the planarwaveguide 600 in FIG. 6) that provides AR/MR/VR functionality when theuser looks through a particular portion of the display. The FOV 1250 maycorrespond to the solid angle that is perceivable by the user whenlooking through the AR display.

As the user's pose changes (e.g., head pose or eye pose), the FOV 1250will correspondingly change, and the objects within the FOV 1250 mayalso change. For example, the map 1210 is initially outside the user'sFOV in FIG. 12. If the user looks toward the map 1210, the map 1210 maymove into the user's FOV 1250, and for example, the object 1230 may moveoutside the user's FOV 1250. As will be described herein, the wearablesystem may keep track of the objects in the FOR 1200 as well as theobjects in the FOV 1250.

The user can interact with interactable objects within the user's FOR1200 and in particular with interactable objects within the user'scurrent FOV 1250 through the wearable system. The interactable objectsmay be physical objects or virtual objects. For example, the object 1230may be a virtual graph that shows the change in price of a stock overtime. By selecting the virtual object 1230, the user may interact withthe virtual object 1230 to, for example, obtain stock quotes, buy orsell the stock, obtain information about the company, etc. To performthese interactions, the wearable system may display menus, toolbars,etc., associated with the virtual object, which can permit the user toperform various actions (e.g., obtaining the stock quote).

The user can interact with objects within the FOV using a variety oftechniques, such as e.g., by selecting the objects, moving the objects,opening a menu or toolbar associated with an object, or choosing a newset of selectable objects. The user may interact with the interactableobjects using hand gestures to actuate a user input device (see e.g.,user input device 466 in FIG. 4), such as, e.g., by clicking on a mouse,tapping on a touch pad, swiping on a touch screen, hovering over ortouching a capacitive button, pressing a key on a keyboard or a gamecontroller (e.g., a 5-way d-pad), pointing a joystick, wand, or totemtoward the object, pressing a button on a remote control, or otherinteractions with a user input device. The user may also interact withinteractable objects using head, eye, hand, foot, or other body poses,such as, e.g., gazing or pointing with an arm at an object for a periodof time, tapping foot, blinking eyes for a certain number of timesduring a threshold time interval. These hand gestures on the user inputdevice and poses of the user can cause the wearable system to initiate aselection event in which, for example a user interface operation isperformed (a menu associated with the target interactable object isdisplayed, a gaming operation is performed on an avatar in a game,etc.).

In some implementations, the HMD comprises a light field display that iscapable of displaying virtual objects at different depth planes relativeto the user. The virtual objects can be grouped and displayed atdifferent fixed depth planes. The user's FOV can include multiple depthplanes. Accordingly, the virtual objects depicted in FIG. 12 can, butneed not be, at different apparent distances from the user.

Examples of Notifying a User of Objects in the FOR

FIG. 13 schematically illustrates an example of informing the user of anobject in the user's FOR. The FOR 1200 of a user 1310 has multipleobjects such as, e.g. object 1302 a, object 1304 a, and object 1352. Theobject 1352 is within the user's FOV 1250 while the objects 1302 a and1304 a are outside of the user's FOV but inside of the user's FOR 1200.Any of the objects 1302 a, 1304 a, 1352 can be virtual objects orphysical objects.

In certain implementations, an object in the FOR may be a hidden objectsuch that a user cannot directly perceive the object via the display220. The display 220, however, can present the hidden object when theuser actuates a user input device or when the user uses certain poses(such as, e.g. head, body, or eye pose). For example, as illustrated inFIG. 13, the object 1352 may initially be hidden from the user's view.But the display can show the object 1352 if the user clicks on the userinput device 466.

The wearable system can provide an indication of an object outside of auser's FOV by placing a visual aura near the edge of the user's FOV. InFIG. 13, the wearable system can place one aura 1304 b for the object1304 a and another aura 1302 b for the object 1302 a on the edge of theuser's FOV 1250.

The wearable system can calculate a visual representation of the visualaura based on contextual information associated with the correspondingobject, the environment, or the user (such as, e.g., the pose of theuser, or the user's preference). The visual representation of the visualaura can include shape, color, brightness, position, orientation, size,or other visual effects or characteristics of the visual aura.

To determine the visual representation of the visual aura based on thecontextual information of a corresponding object, the wearable systemcan use a variety of characteristics associated with the correspondingobjects, such as, e.g., location of the object (including the proximityof the object relative to the user), urgency of the object, type of theobject (such as, e.g., interactive v. not interactable, physical v.virtual, an operating system object v. a game object), property of theobject (such as e.g. enemy's avatar v. friend's avatar), volume ofinformation (such as, e.g., number of notifications), etc. As an exampleof calculating the visual representation of the visual aura based on thelocation of the corresponding object, the aura 1304 b may appear thinnerthan the aura 1302 b because the object 1304 a is further away from theuser's FOV than the object 1302 a. As another example, the aura 1302 bmay have a larger and brighter appearance because the object 1302 a ismore urgent and/or closer to the user's FOV. The visual representationof the visual aura may change over time based on a change of the objectassociated with the visual aura. For example, the aura 1304 b may getbigger (or brighter) as the object 1304 a moves closer to the user's FOVor may grow smaller (or dimmer) as the object 1304 a moves away from theuser's FOV.

In certain implementations, the visual representation of the aura can bedetermined based on the existing volume of information of thecorresponding object. For example, the object 1302 a may be a messagingapplication which can be configured to receive and send messages for theuser 1310. As the object 1302 receives more messages, the aura 1302 bcan grow thicker to indicate the accumulation of messages.

The wearable system may assign a color to an aura based on thecharacteristics of the associated object. For example, the wearablesystem may assign a red color to the aura 1304 b because the object 1304a is associated with the red color. Similarly, the AR system may assigna blue color to the object 1302 b because it is an operating systemobject and the AR system assigns the blue color to all operating systemobjects. The assigned color is not limited to being a single color butmay include multiple colors, shadings, contrasts, saturations, etc. Thevisual representation of the aura may also include visual effects suchas, e.g., animations (e.g., translating or rotating the aura), fading inor out, etc. The visual representation of the aura may be accompanied bya sound, a tactile sensation, etc.

The wearable system can also determine the visual representation of thevisual aura based on a user's pose. For example, as the user 1310 turnsleftwards, the object 1304 a may become closer to the user's FOV whilethe object 1302 a may be farther away from the user's FOV. As a result,the aura 1304 b may become brighter (or larger) while the aura 1302 bmay become dimmer (or smaller). The position of aura may change as theobjects and/or user moves. For example, the AR system may show the aura1304 b on the right side of the FOV 1250 when the object 1304 a moves tothe right side of the user 1310.

In addition to or in alternative to determining the visualrepresentation of the visual aura based on characteristics of theobjects or the user's pose, the wearable system can use contextualinformation associated with the user's environment to determine thevisual representation of the visual aura. The contextual informationassociated with the user's environment can include the light conditionof the environment. The light conditions may be based on the environmentas perceived by the user through the display 220. The environment asperceived by the user could be the user's physical surroundings such asthe user's room or virtual environments (such as, e.g., a simulatedjungle in a game). With reference to FIG. 13, the aura 1304 b mayinitially be invisible to the user 1310. This may be because the userperceives a dark environment through the display 220. Since dark objectsare typically not perceptible, the wearable system may not display anaura for objects in the dark environment. However, the wearable systemcan show the aura 1304 b on the edge of the user's FOV when a lightilluminates the object 1304 a. The light can come from one or more offscreen objects, light sources (real or virtual), etc.

In certain embodiments, the visual representation of the aura cancorrespond to optical effects of objects under the light condition ofthe environment. For example, the shape of the aura (e.g. an oval) maybe the two-dimensional projection of the object (e.g. a football)associated with the aura. In this example, the visual aura can appear asif the football is projected onto the edge of the user's FOV.

When an aura corresponds to a virtual object, the wearable system cansimulate optical effects of the virtual object as if it is a physicalobject. For example, in FIG. 13, the object 1304 a may be a virtualobject which can reflect red color if it is a physical object.Accordingly, the display 220 of the wearable system 220 may display theaura 1304 b as having a red color (illustrated in a cross-hatchedpattern) when a light is shined on the object 1304 a.

The optical effects can also incorporate location information of theobject. For example, when an object is behind the user, the shape of thereflected object is naturally longer and thinner. The user can use thisshape to differentiate this object from another object which is to theimmediate right or left of the user's FOV. For example, in FIG. 13, theobject 1304 a is farther away and behind the user (e.g., as compared tothe object 1302 a). Accordingly, the aura 1304 b may have a thin shapewith low brightness. The aura 1302 b, however, is thicker and shorterbecause the object 1302 a is immediately to the right of the user's FOV.

The wearable system can render a visual representation of the aura withthe display 220. The wearable system can render at least a portion ofthe visual representation of the aura near the FOV 1250 of the user. Insome embodiments, when an object is within the FOV 1250, the wearablesystem can be configured not to determine the corresponding aura. Inother embodiments, the wearable system can still determine the visualrepresentation of the aura even though the object is within the FOV1250. Rather, the wearable system can be configured not to render thevisual representation of an aura for an object within the FOV becausethe object is perceivable by the user. As shown in FIG. 13, the object1352 is within the user's FOV 1250 but the wearable system can beconfigured not to project an aura onto the edge of the FOV for theobject 1352.

In certain implementations, although the object within the FOV may stillhave its corresponding aura, the wearable system can be configured tohide the visual representation of aura (e.g., such that the user willnot perceive the aura) through optical effects associated with thedisplay 220. For example, where the visual representation of the aura isdetermined in accordance with the light conditions, the interior surfaceedge of an aura (corresponding to an object inside of the FOV) can beconfigured to co-linearly align with wearable system's the imagingsystem (such as, e.g., a simulated light source and/or cameras shown inFIG. 2) or the user's eye(s). In such examples, the user will notperceive reflections from the interior surface edge caused by lightsources within the FOV, and therefore will not perceive the auracorresponding to the object inside of the FOV.

Besides visual auras, the wearable system can also inform the user aboutobjects outside of the user's FOV using a tactile or an audio effect.For example, in an augmented reality game, the wearable system maynotify the user of an approaching enemy through vibrations on a userinput device. The wearable system may provide strong vibrations when theenemy is close to the user while provide weak vibrations when the enemyis relatively far away from the user. In another example, the wearablesystem can use audible sounds to provide position information of avirtual object. The wearable system may use a loud sound to alarm theuser of a virtual enemy which is nearby. The wearable system can alsosimulate a sound field which reflects the spatial locations of thevirtual object. The tactile, audio, or visual aura can be used incombination or in alternative to inform the user about the surroundingobjects.

Example Visual Presentations of an Aura

FIG. 14A schematically illustrates a perspective view of visual auras onan edge of an FOV. In this example, the edge 1410 is the area that is atthe outer boundary of the FOV 1250. The edge 1410 of the FOV 1250 cancomprise an outer rim 1412 and an inner rim 1414. The edge may have awidth 1416. The wearable system can place a portion of the aura on edge1410 of the FOV 1250. For example, a portion of the aura 1402 b is onthe edge 1410 of the FOV 1250. As another example, the wearable systemcan place the entire aura 1404 b in between the outer rim 1412 and theinner rim 1414. The auras may have a variety of sizes. Some auras mayhave a diameter smaller than or equal to the width 1416 of the edge 1410of the FOV 1250, while other auras may have a diameter greater than thewidth 1416 of the edge 1410 of the FOV 1250.

The wearable system can determine and render visual representations ofan aura separately for each eye to match human peripheral vision. Forexample, the wearable system may render a visual representation of theaura 1402 b for only the right eye instead of both eyes because thelocation of the object 1402 a is not within the FOV of the left eye.This technique can also be used to simulate human eye experience ofobserving an object's movements. For example, the wearable system candetermine the visual representation of the aura to simulate the effectof the object fading out the left edge of the right eye and the rightedge of the left eye.

By presenting auras separately for each eye, the wearable system canreduce the likelihood that the human eyes resolve the aura at depthbecause the aura for each eye does not match stereoscopically.Advantageously, in some embodiments, this reduces visual competitionbetween the auras and other virtual content perceived through thewearable system.

FIG. 14B schematically illustrates an example of making a correspondingaura invisible for an object within the user's FOV. As shown in FIG.14B, there can be a distance between the human eye 1488 and the edge1410 of the FOV as perceived by the user through the wearable system.There can be a FOV angle 1420 when a user uses the HMD. The degree ofthe FOV angle 1420 may be determined based on the distance between thehuman eye and the edge 1410. The degree of the FOV angle 1420 may alsobe based on the physical and chemical characteristics of the display220. As the degree of FOV angle 1420 changes, the visual representationof the aura may also change.

As described with reference to FIG. 13, the wearable system maydetermine the visual representation of the aura by simulating lightconditions in the user's environment. Such light conditions can beapplied to both objects within the FOV and objects outside of the FOV.The wearable system can place the aura for an object within the user'sFOV in a way such that the user will not be able to see the auraassociated with the object within the user's FOV. For example, in FIG.14B, the aura 1452 can be associated with the object 1352 (shown in FIG.14A). The wearable system can be configured to position the interiorsurface edge of the aura 1452 to be co-linearly aligned with the imagingsystem of the wearable system or the eye of the user. In thisconfiguration, the user may not see the inside edge of the aura 1452.

Example User Experience with a Visual Aura

FIGS. 15A and 15B schematically illustrate examples of user experiencewith a visual aura. In FIG. 15A, the user 1210 can stand in a room. Theuser 1210 can a FOR 1250 and a FOV 1250 when the user 1210 wears an HMD.The object 1552 is within the user's FOV. The object 1552 may be anobject in an application. For example, in FIG. 15A, the object 1552 maybe a virtual creature that the user 1210 perceives through the display220.

As shown in FIG. 15A, the object 1502 a is within the user's FOR 1200but is outside of the user's FOV 1250. The object 1502 a may be anobject associated with an operating system. For example, as indicated inFIG. 15A, the object 1502 a can be a home object which can direct theuser to the main page of the user's HMD. The wearable system can show aportion of the visual aura 1502 b of the object 1502 a on the edge 1410of the FOV 1250. The wearable system can determine a visualrepresentation of the aura using various contextual factors describedwith reference to FIGS. 13, 14A, and 14B and render the visualrepresentation of the visual aura 1502 b accordingly.

When a user changes his pose (such as by tilting his head), the object1502 a can move inside the user's FOV 1250 as shown in FIG. 15B. In someembodiments, the display 220 of the wearable system will not show theaura for the object 1502 a when it is inside of the FOV 1250. In otherembodiments, the wearable system may be configured to make the interiorsurface edge of the aura 1502 a to be co-linearly aligned with thewearable system's the imaging system (such as, e.g., simulated lightsource and/or cameras shown in FIG. 2) or with the user's eye(s).Accordingly, the user may not be able to perceive the aura if the object1502 a is within the FOV 1250.

Example Processes of Determining a Visual Representation of an Aura

FIG. 16 illustrates an example process of rendering a visualrepresentation of a visual aura. The process 1600 can be performed bythe wearable system described herein (see e.g. wearable system describedwith reference to FIGS. 2 and 4).

At block 1610, the wearable system determines a group of virtual objectsin the user's FOR. The group of virtual objects can be a subset ofobjects in the user's environment. In certain embodiments, the virtualobjects may be hidden from a user's view.

At block 1620, the wearable system can determine the user's pose. Theuser's pose may be the head, eye, body pose, alone or in combination.The wearable system can determine the user's pose based on data acquiredfrom a variety of sensors, such as e.g., an inward-facing imaging system(see, e.g. the inward-facing imaging system 462 in FIG. 4), inputsreceived on a user input device (see e.g. user input device 466 in FIG.4), FOV camera and/or sensors (see descriptions with reference to FIG.10).

At block 1630, the wearable system can determine the user's FOV based onthe user's pose. The FOV can comprise a portion of the FOR that isperceived at a given time by the user.

Based on the user's FOV, at block 1640, the wearable system can identifya virtual object which is inside of the FOR but outside of the FOV ofthe user. In some implementations, the wearable system may be configuredto display auras for some objects in the user's FOR. The wearable systemcan identify the virtual object for which a visual aura is renderedbased on the contextual information described herein. For example, thewearable system can be configured to render the visual aura based on thetype of virtual object, where the wearable system can render the visualaura if the virtual object is interactable. As another example, thewearable system will render the visual aura if the virtual object iswithin a threshold distance from the user. As yet another example, thewearable system can be configured to sort the virtual objects (that areoutside of the FOV) based on the contextual information and the wearablesystem may only render an aura associated with the most urgent object.In certain implementations, the wearable system can display auras forall virtual objects in the FOR.

In the situation where a virtual object is a hidden object, the visualaura can provide a cue on the direction and position of the hiddentreasure. For example, in a treasure hunt game, the visual aura canprovide an indication of the location of the hidden treasure. In someembodiments, one visual aura can correspond to more than one object. Forexample, the wearable system can render a visual aura indicating a setof office tools is available right next to the user's current position.

At block 1650, the wearable system can determine a visual representationof a visual aura associated with the virtual object. The wearable systemcan use a variety of contextual factors to determine the visualrepresentation of the aura. For example, the wearable system maycalculate the location of the virtual object relative to the FOV of theuser. In certain embodiments, the wearable system can determine thevisual representation using the local processing and data module 260alone or in combination with the remote processing module 270 (shown inFIG. 2). For example, the remote processing module 260 can determine acolor of the visual aura, while the local processing and data module 260can determine the location and size of the visual aura. As anotherexample, the remote processing module 270 can determine a default visualrepresentation while the local processing and data module 260 can trackthe movements of the user (or the virtual object corresponding to theaura) and adjust the default visual representation accordingly. Forexample, local processing and data module 260 can access the defaultvisual representation of the aura from the remote data repository andadjust the size and brightness of the default visual representation ofthe aura based on the virtual object's position relative to the user'sFOV.

At block 1660, the wearable system can render the visual representationof the visual aura. The visual representation can be rendered based onthe determination in the block 1650. A portion of the visual aura may beplaced on the edge of the user's FOV. In some situations where there aremultiple visual auras to be displayed, the wearable system may place aportion of a visual aura to overlap with a portion of another visualaura. As described herein, the wearable system may renderrepresentations of the aura separately for each eye. The separatepresentations may be able to match human peripheral vision and tosimulate human eye experience of observing an object's movements. Incertain implementations, the visual aura of a virtual object will berendered on the edge of the FOV for one eye but not for the other eye.

Although the example process 1600 is described with reference torendering visual representations of the aura associated with a virtualobject, in certain embodiments, the aura may also be associated with aphysical object (such as, e.g., a television, a coffee-maker, etc.).

FIG. 17 illustrates an example process of determining a visualrepresentation of the visual aura based on contextual information. Theprocess 1700 can be performed by the wearable system described herein(see e.g. wearable system described with reference to FIGS. 2 and 4).

At block 1710, the wearable system can identify an object in the user'senvironment. The object may be a physical object or a virtual object,and the environment may be the user's physical or virtual environment.The wearable system can identify the objects using the techniquesdescribed with reference to the process 1600 in FIG. 16. In certainembodiments, the object identified in the user's environment may be ahidden object. The hidden object may be occluded (e.g. blocked byanother object) from a user's view or may become perceivable upon a userinterface operation, such as, e.g., an actuation of the user inputdevice 466 or a change in the user's pose.

As described with reference to FIG. 16, the wearable system can identifythe object based on the user's FOV. The FOV of the user may bedetermined based on the optical characteristics of the display of thewearable system and the user's pose (such as a body pose or a head pose)as described herein. In some embodiments, the identified object isoutside of the user's FOV but is inside of the FOR. The wearable systemcan determine whether an object is outside of the user's FOV using aworld map 920 (described in FIG. 9) of the user's environment. Forexample, the wearable system can determine the user's current locationand position the user in the world map. The wearable system canaccordingly calculate the objects that are inside of the FOV based onthe user's position in the world map.

At block 1720, the wearable system can access contextual informationassociated with the object, the user, or the environment. The contextualinformation may be used to determine (or access) a visual representationof the aura corresponding to the object at block 1730. For example, amore urgent object may be associated with a larger and brighter aurawhile a less urgent object may be associated with a smaller or dimmeraura. As another example, the aura may represent a 2D projection of theobject (onto the edge of the FOV) under the light conditions of theuser's environment.

Optionally, at block 1740, the wearable system can render the visualrepresentation of the aura based on the determination at block 1730.Examples of the visual representation of the aura have been describedwith reference to FIGS. 13-15B. In some cases, the wearable system maynot render the visual representation of the aura. For example, if theobject is within the FOV, the system may presume that the user can seethe object and an aura may not be needed. If the system wishes to callthe user's attention to an object in the FOV, the system may render anaura associated with the object (e.g., at least partially surroundingthe object) to alert the user to the object. As another example, if theobject is behind the user (e.g., in the user's FOR but not in the user'sFOV), the wearable system may not render the visual representationbecause the user occludes the projection of the object onto an edge ofthe FOV. As another example and as described with reference to FIG. 14B,the object may be projected onto the edge of the FOV such that theposition of the interior surface edge of the aura 1452 is co-linearlyaligned with the imaging system of the AR system or the eye of the user.In this configuration, the user may not see the inside edge of the aura1452.

Where the object is outside of the FOV but is inside of the FOR, thevisual representation of the aura can be rendered as described withreference to block 1660 in FIG. 16.

Although the examples describe herein can provide auras for objects thatare inside the FOV or inside the FOR but outside of the FOV, in variousembodiments, the auras can also be provided for an object that isoutside of the FOV and the FOR. For example, in a video game, a virtualenemy may be hiding behind a wall or approaching the user from adifferent room that is outside of the user's FOR. The wearable systemcan provide a visual aura on the edge of the user's FOV as a cue for thelocation of the virtual enemy. In certain implementations, the user candetermine whether to turn off the visual auras for certain objects. Forexample, once a user has advanced to certain levels in a game, the usermay turn off the visual aura features such that the wearable system willnot provide a visual aura for an approaching enemy.

Additional Embodiments

In a 1st aspect, a method for providing an indication regarding presenceof a virtual object in an augmented reality environment around a user,the method comprising: under control of an augmented reality (AR) systemcomprising computer hardware, the AR system configured to permit userinteraction with virtual objects in a field of regard (FOR) of the user,the FOR comprising a portion of the environment around the user that iscapable of being perceived by the user via the AR system: determining agroup of virtual objects in the FOR of the user; determining a pose ofthe user; determining a field of view (FOV) of the user based at leastpartly on the pose of the user, the FOV comprising a portion of the FORthat is capable of being perceived at a given time by the user via theAR system; identifying a subgroup of the group of virtual objects thatare located inside of the FOR of the user but outside of the FOV of theuser; for at least some of the virtual objects in the subgroup ofvirtual objects: determining a location of the virtual object relativeto the FOV of the user; determining, based at least in part on thelocation, a placement of a visual aura associated with the virtualobject relative to the FOV of the user; and displaying the visual aurasuch that at least a portion of the visual aura is perceivable by theuser to be on an edge of the FOV of the user. In some embodiments, theplacement of the visual aura is also referred to as the visualrepresentation of the visual aura.

In a 2nd aspect, the method of aspect 1, wherein the pose of the usercomprises an eye pose of the user.

In a 3rd aspect, the method of any one of aspects 1-2, wherein thevisual aura comprises a shape having a color.

In a 4th aspect, the method of aspect 3, wherein the shape comprises arounded square.

In a 5th aspect, the method of any one of aspects 3-4, wherein the colorof the visual aura indicates a type of the virtual object.

In a 6th aspect, the method of any one of aspects 1-5, wherein theplacement of the aura comprises one or more of the following:brightness, position, or size.

In a 7th aspect, the method of aspect 6, wherein the brightness is basedat least in part on proximity of the virtual object relative to the edgeof the FOV.

In an 8th aspect, the method of any one of aspects 6-7, wherein the sizeindicates the proximity and/or urgency of the virtual objects.

In a 9th aspect, the method of any one of aspects 1-8, wherein the FOVof the user is determined based at least partly on an area of an ARdisplay in the AR system.

In a 10th aspect, the method of any one of aspects 1-9, wherein thevirtual objects comprise one or more of the following: an operatingsystem virtual object or an application virtual object.

In an 11th aspect, the method of any one of aspects 1-10, wherein the ARsystem comprises a first AR display for a first eye of the user and asecond AR display for a second eye of the user, and wherein displayingthe visual aura on the edge of the FOV of the user comprises: displayinga first representation of the visual aura by the first AR display.

In a 12th aspect, the method of aspect 11, further comprising displayinga second representation of the visual aura by the second AR display, thesecond representation different from the first representation.

In a 13th aspect, the method of aspect 12, wherein the firstrepresentation of the visual aura and the second representation of thevisual aura are rendered separately to each eye to match peripheralvision.

In a 14th aspect, the method of any one of aspects 12-13, wherein thefirst representation of the visual aura the second representation of thevisual aura are rendered separately to each eye to reduce or avoid depthperception of the visual aura.

In a 15th aspect, the method of any one of aspects 1-14, furthercomprising: updating the subgroup of the group of virtual objects basedat least partly on a change of the pose of the user; and updating thefirst or second representation of the visual aura based on the updatedsubgroup of the group of virtual objects.

In a 16th aspect, the method of any one of aspects 1-15, furthercomprising: determining that a virtual object in the subgroup of virtualobjects has moved inside of the FOV of the user; and ceasing to displaythe visual aura associated with that virtual object.

In a 17th aspect, the method of any one of aspects 1-16, furthercomprising: determining that a virtual object in the FOV of the user hasmoved outside of the FOV of the user; and displaying a visual auraassociated with that virtual object.

In an 18th aspect, a method for providing an indication of an object inan environment of a user, the method comprising: under control of anaugmented reality (AR) system comprising an imaging system, the ARsystem configured to permit user interaction with virtual objects in afield of regard (FOR) of the user, the FOR comprising a portion of theenvironment around the user that is capable of being perceived by theuser via the AR system: determining a group of objects in the FOR of theuser; determining a field of view (FOV) of the user, the FOV comprisinga portion of the FOR that is capable of being perceived at a given timeby the user via the AR system; identify a subgroup of the group ofobjects that are located inside of the FOR of the user but outside ofthe FOV of the user; and displaying a visual aura for one or more of theobjects in the subgroup of the group of objects such that at least aportion of the visual aura is perceivable in the FOV of the user.

In a 19th aspect, the method of aspect 18, wherein the FOV is determinedbased at least partly on a pose of the user.

In a 20th aspect, the method of aspect 19, wherein the pose of the usercomprises at least one of the following: head pose, eye pose, or bodypose.

In a 21st aspect, the method of any one of aspects 18-20, furthercomprising: determining a light condition of the environment of theuser; simulating optical effects of the light condition for one or morevirtual objects in the group of the objects; and determining a placementof the visual aura associated with the one or more virtual objects basedat least partly on the simulated optical effects.

In a 22nd aspect, the method of aspect 21, wherein the environment isone or more of virtual environment or physical environment.

In a 23rd aspect, the method of any one of aspects 21-22, wherein theplacement of the aura comprises one or more of the following:brightness, position, shape, or size.

In a 24th aspect, the method of any one of aspects 21-23, whereindetermining a placement of the visual aura further comprises: identify avirtual object in the subgroup of the group of objects which are in theFOR of the user but are outside of the FOV of the user; and collinearlyalign the imaging system and at least one eye of the user with aninterior edge of a visual aura associated with the virtual object.

In a 25th aspect, the method of any one of aspects 18-24, wherein the ARsystem comprises a first AR display for a first eye of the user and asecond AR display for a second eye of the user, and wherein displayingthe visual aura on the edge of the FOV of the user comprises: displayinga first representation of the visual aura by the first AR display.

In a 26th aspect, the method of aspect 25, further comprising displayinga second representation of the visual aura by the second AR display, thesecond representation different from the first representation.

In a 27th aspect, the method of aspect 26, wherein the firstrepresentation of the visual aura and the second representation of thevisual aura are rendered separately to each eye to match peripheralvision.

In a 28th aspect, the method of any one of aspects 26-27, wherein thefirst representation of the visual aura the second representation of thevisual aura are rendered separately to each eye to reduce or avoid depthperception of the visual aura.

In a 29th aspect, the method of any one of aspects 18-28, furthercomprising: updating the subgroup of the group of objects based at leastpartly on a change of the pose of the user; and updating the first orsecond representation of the visual aura based on the updated subgroupof the group of objects.

In a 30th aspect, an augmented reality (AR) system comprising computerhardware programmed to perform the method of any one of aspects 1-29.

In a 31st aspect, a system for providing an indication of aninteractable object in a three-dimensional (3D) environment of a user,the system comprising: a display system of a wearable device configuredto present a three-dimensional view to a user and permit a userinteraction with objects in a field of regard (FOR) of a user, the FORcomprising a portion of the environment around the user that is capableof being perceived by the user via the display system; a sensorconfigured to acquire data associated with a pose of the user; and ahardware processor in communication with the sensor and the displaysystem, the hardware processor programmed to: determine a pose of theuser based on the data acquired by the sensor; determine a field of view(FOV) of the user based at least partly on the pose of the user, the FOVcomprising a portion of the FOR that is capable of being perceived at agiven time by the user via the display system; identify an interactableobject located outside of the FOV of the user; access contextualinformation associated with the interactable object; determine a visualrepresentation of an aura based on the contextual information; andrender the visual representation of the aura such that at least aportion of the visual aura perceivable by the user is on an edge of theFOV of the user.

In a 32nd aspect, the system of aspect 1, wherein the display systemcomprises a first light field display for a first eye of the user and asecond light field display for a second eye of the user, and wherein torender a visual representation of the aura, the hardware processor isprogrammed to: render a first visual representation of the aura by thefirst light field display at a first edge of a first FOV associated withthe first eye; and render a second visual representation of the aura bythe second light field display at a second edge of the second FOVassociated with the second eye.

In a 33rd aspect, the system of aspect 32, wherein the firstrepresentation of the aura and the second representation of the aura arerendered separately for each eye to match the user's peripheral vision.

In a 34th aspect, the system of any one of aspects 31-33, wherein thecontextual information comprises information associated with the user,the 3D environment, or characteristics of the interactable object.

In a 35th aspect, the system of aspect 34, wherein the informationassociated with the 3D environment comprises a light condition of theenvironment of the user, and wherein the placement of the aura isdetermined by simulating an optical effect of the interactable objectunder the light condition.

In a 36th aspect, the system of any one of aspects 31-35, wherein thehardware processor is further programmed to: detect a change in the poseof the user; determine an updated location of the interactable object inthe 3D environment based on the change in the pose of the user; andupdate the visual representation of the aura based on the updatedlocation of the interactable object.

In a 37th aspect, the system of aspect 36, wherein in response to adetermination that the updated location is within the user's FOV, thehardware processor is programmed to determine the placement of the auraby collinearly aligning an interior edge of the aura with at least oneeye of the user.

In a 38th aspect, the system of any one of aspects 31-37, wherein thevisual representation of the aura comprising at least one of: aposition, a shape, a color, a size, or a brightness.

In a 39th aspect, the system of aspect 8, wherein the size of the auraindicates at least one of: a proximity or an urgency of the interactableobject.

In a 40th aspect, the system of any one of aspects 31-39, wherein thepose of the user comprises at least one of: a head pose or a directionof gaze.

In a 41st aspect, a method for providing an indication of aninteractable object in a three-dimensional (3D) environment of a user,the method comprising: under control of a wearable device having adisplay system configured to present a three-dimensional (3D) view to auser and permit a user interaction with objects in a field of regard(FOR) of a user, the FOR comprising a portion of the environment aroundthe user that is capable of being perceived by the user via the displaysystem; a sensor configured to acquire data associated with a pose ofthe user; and a hardware processor in communication with the sensor andthe display system: determining a field of view (FOV) of the user basedat least partly on the pose of the user, the FOV comprising a portion ofthe FOR that is capable of being perceived at a given time by the uservia the display system; identifying an interactable object locatedoutside of the FOV of the user; accessing contextual informationassociated with the interactable object; determining a visualrepresentation of an aura based on the contextual information; andrendering the visual representation of the aura such that at least aportion of the visual aura perceivable by the user is on an edge of theFOV of the user.

In a 42nd aspect, the method of aspect 41, further comprising: renderinga first visual representation of the aura at a first edge of a first FOVassociated with a first eye of the user; and rendering a second visualrepresentation of the aura at a second edge of the second FOV associatedwith a second eye of the user.

In a 43rd aspect, the method of aspect 42, wherein the firstrepresentation of the aura and the second representation of the aura arerendered separately for each eye to match the user's peripheral vision.

In a 44th aspect, the method of any one of aspects 41-43, wherein thecontextual information comprises information associated with the user,the 3D environment, or characteristics of the interactable object.

In a 45th aspect, the method of aspect 44, wherein the informationassociated with the 3D environment comprises a light condition of theenvironment of the user, and wherein the visual representation of theaura is determined by simulating an optical effect of the interactableobject under the light condition.

In a 46th aspect, the method of aspect 45, further comprising: detectinga change in the pose of the user; determining an updated location of theinteractable object in the 3D environment based on the change in thepose of the user; and updating the visual representation of the aurabased on the updated location of the interactable object.

In a 47th aspect, the method of aspect 46, wherein in response to adetermination that the updated location is within the user's FOV,collinearly aligning an interior edge of the aura with at least one eyeof the user.

In a 48th aspect, the method of any one of aspects 46-47, wherein thevisual representation of the aura comprising at least one of: aposition, a shape, a color, a size, or a brightness.

In a 49th aspect, the method of aspect 48, wherein the size of the auraindicates at least one of: a proximity or an urgency of the interactableobject.

In a 50th aspect, the method of any one of aspects 41-49, wherein thepose of the user comprises at least one of: a head pose or a directionof gaze.

CONCLUSION

Each of the processes, methods, and algorithms described herein and/ordepicted in the attached figures may be embodied in, and fully orpartially automated by, code modules executed by one or more physicalcomputing systems, hardware computer processors, application-specificcircuitry, and/or electronic hardware configured to execute specific andparticular computer instructions. For example, computing systems caninclude general purpose computers (e.g., servers) programmed withspecific computer instructions or special purpose computers, specialpurpose circuitry, and so forth. A code module may be compiled andlinked into an executable program, installed in a dynamic link library,or may be written in an interpreted programming language. In someimplementations, particular operations and methods may be performed bycircuitry that is specific to a given function.

Further, certain implementations of the functionality of the presentdisclosure are sufficiently mathematically, computationally, ortechnically complex that application-specific hardware or one or morephysical computing devices (utilizing appropriate specialized executableinstructions) may be necessary to perform the functionality, forexample, due to the volume or complexity of the calculations involved orto provide results substantially in real-time. For example, a video mayinclude many frames, with each frame having millions of pixels, andspecifically programmed computer hardware is necessary to process thevideo data to provide a desired image processing task or application ina commercially reasonable amount of time.

Code modules or any type of data may be stored on any type ofnon-transitory computer-readable medium, such as physical computerstorage including hard drives, solid state memory, random access memory(RAM), read only memory (ROM), optical disc, volatile or non-volatilestorage, combinations of the same and/or the like. The methods andmodules (or data) may also be transmitted as generated data signals(e.g., as part of a carrier wave or other analog or digital propagatedsignal) on a variety of computer-readable transmission mediums,including wireless-based and wired/cable-based mediums, and may take avariety of forms (e.g., as part of a single or multiplexed analogsignal, or as multiple discrete digital packets or frames). The resultsof the disclosed processes or process steps may be stored, persistentlyor otherwise, in any type of non-transitory, tangible computer storageor may be communicated via a computer-readable transmission medium.

Any processes, blocks, states, steps, or functionalities in flowdiagrams described herein and/or depicted in the attached figures shouldbe understood as potentially representing code modules, segments, orportions of code which include one or more executable instructions forimplementing specific functions (e.g., logical or arithmetical) or stepsin the process. The various processes, blocks, states, steps, orfunctionalities can be combined, rearranged, added to, deleted from,modified, or otherwise changed from the illustrative examples providedherein. In some embodiments, additional or different computing systemsor code modules may perform some or all of the functionalities describedherein. The methods and processes described herein are also not limitedto any particular sequence, and the blocks, steps, or states relatingthereto can be performed in other sequences that are appropriate, forexample, in serial, in parallel, or in some other manner. Tasks orevents may be added to or removed from the disclosed exampleembodiments. Moreover, the separation of various system components inthe implementations described herein is for illustrative purposes andshould not be understood as requiring such separation in allimplementations. It should be understood that the described programcomponents, methods, and systems can generally be integrated together ina single computer product or packaged into multiple computer products.Many implementation variations are possible.

The processes, methods, and systems may be implemented in a network (ordistributed) computing environment. Network environments includeenterprise-wide computer networks, intranets, local area networks (LAN),wide area networks (WAN), personal area networks (PAN), cloud computingnetworks, crowd-sourced computing networks, the Internet, and the WorldWide Web. The network may be a wired or a wireless network or any othertype of communication network.

The systems and methods of the disclosure each have several innovativeaspects, no single one of which is solely responsible or required forthe desirable attributes disclosed herein. The various features andprocesses described above may be used independently of one another, ormay be combined in various ways. All possible combinations andsubcombinations are intended to fall within the scope of thisdisclosure. Various modifications to the implementations described inthis disclosure may be readily apparent to those skilled in the art, andthe generic principles defined herein may be applied to otherimplementations without departing from the spirit or scope of thisdisclosure. Thus, the claims are not intended to be limited to theimplementations shown herein, but are to be accorded the widest scopeconsistent with this disclosure, the principles and the novel featuresdisclosed herein.

Certain features that are described in this specification in the contextof separate implementations also can be implemented in combination in asingle implementation. Conversely, various features that are describedin the context of a single implementation also can be implemented inmultiple implementations separately or in any suitable subcombination.Moreover, although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to asubcombination or variation of a subcombination. No single feature orgroup of features is necessary or indispensable to each and everyembodiment.

Conditional language used herein, such as, among others, “can,” “could,”“might,” “may,” “e.g.,” and the like, unless specifically statedotherwise, or otherwise understood within the context as used, isgenerally intended to convey that certain embodiments include, whileother embodiments do not include, certain features, elements and/orsteps. Thus, such conditional language is not generally intended toimply that features, elements and/or steps are in any way required forone or more embodiments or that one or more embodiments necessarilyinclude logic for deciding, with or without author input or prompting,whether these features, elements and/or steps are included or are to beperformed in any particular embodiment. The terms “comprising,”“including,” “having,” and the like are synonymous and are usedinclusively, in an open-ended fashion, and do not exclude additionalelements, features, acts, operations, and so forth. Also, the term “or”is used in its inclusive sense (and not in its exclusive sense) so thatwhen used, for example, to connect a list of elements, the term “or”means one, some, or all of the elements in the list. In addition, thearticles “a,” “an,” and “the” as used in this application and theappended claims are to be construed to mean “one or more” or “at leastone” unless specified otherwise.

As used herein, a phrase referring to “at least one of” a list of itemsrefers to any combination of those items, including single members. Asan example, “at least one of: A, B, or C” is intended to cover: A, B, C,A and B, A and C, B and C, and A, B, and C. Conjunctive language such asthe phrase “at least one of X, Y and Z,” unless specifically statedotherwise, is otherwise understood with the context as used in generalto convey that an item, term, etc. may be at least one of X, Y or Z.Thus, such conjunctive language is not generally intended to imply thatcertain embodiments require at least one of X, at least one of Y and atleast one of Z to each be present.

Similarly, while operations may be depicted in the drawings in aparticular order, it is to be recognized that such operations need notbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. Further, the drawings may schematically depict one more exampleprocesses in the form of a flowchart. However, other operations that arenot depicted can be incorporated in the example methods and processesthat are schematically illustrated. For example, one or more additionaloperations can be performed before, after, simultaneously, or betweenany of the illustrated operations. Additionally, the operations may berearranged or reordered in other implementations. In certaincircumstances, multitasking and parallel processing may be advantageous.Moreover, the separation of various system components in theimplementations described above should not be understood as requiringsuch separation in all implementations, and it should be understood thatthe described program components and systems can generally be integratedtogether in a single software product or packaged into multiple softwareproducts. Additionally, other implementations are within the scope ofthe following claims. In some cases, the actions recited in the claimscan be performed in a different order and still achieve desirableresults.

What is claimed is:
 1. A system for providing an indication of a hiddenvirtual object in a three-dimensional (3D) environment of a user, thesystem comprising: a display system of a wearable device configured topresent a three-dimensional view to a user, wherein the display systemcomprises a first light field display for a first eye of the user and asecond light field display for a second eye of the user, and wherein thefirst and second light field displays are configured to render a visualrepresentation of an aura; a sensor configured to acquire dataassociated with a pose of the user; and a hardware processor incommunication with the sensor and the display system, the hardwareprocessor programmed to: identify a virtual object within a Field ofView (FOV) of the user via the display system; calculate a location ofthe virtual object in relation to the pose of the user; render a firstvisual representation of the aura by the first light field display at afirst edge of a first FOV associated with the first eye; and render asecond visual representation of the aura by the second light fielddisplay at a second edge of a second FOV associated with the second eye,wherein the second visual representation does not match stereoscopicallywith the first visual representation and is rendered at a depth that isdifferent than other virtual content rendered by the display system. 2.The system of claim 1, wherein the first representation of the aura andthe second representation of the aura are rendered separately for eacheye to match the user's peripheral vision.
 3. The system of claim 1,wherein the hardware processor is further programmed to: detect a changein the pose of the user; determine an updated location of the virtualobject in the FOV of the user based on the change in the pose of theuser; and update the visual representation of the aura based on theupdated location of the virtual object.
 4. The system of claim 1,wherein the hardware processor is programmed to determine placement ofthe aura by collinearly aligning an interior edge of the aura with atleast one eye of the user.
 5. The system of claim 1, wherein the visualrepresentation of the aura comprising at least one of: a position, ashape, a color, a size, or a brightness.
 6. The system of claim 5,wherein the size of the aura indicates at least one of: a proximity oran urgency of the virtual object.
 7. The system of claim 1, wherein thepose of the user comprises at least one of: a head pose or a directionof gaze.
 8. The system of claim 1, wherein the virtual object comprisesan object occluded from a user's view.
 9. The system of claim 1, whereinthe virtual object becomes perceivable in response to a user interfaceoperation.
 10. The system of claim 1, wherein the virtual objectcomprises a virtual element of a physical object.
 11. The system ofclaim 1, wherein the hardware processor is programmed to: receive a userinput associated with the virtual object; and render the virtual objectin response to the user input.